X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C8757D.ABA4A1EA@onstor-exch02.onstor.net>; Fri, 22 Feb 2008 10:06:39 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C8757D.ABA4A1EA"
Content-class: urn:content-classes:message
Subject: RE: do we support volumes with multiple raid levels luns?
Date: Fri, 22 Feb 2008 10:06:39 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0875EF30@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E05C742F1@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: do we support volumes with multiple raid levels luns?
Thread-Index: Achzd9LL0Ki78BrPR26nIKysplN1/wB+//IgAAFpChAAAPb3AA==
References: <BB375AF679D4A34E9CA8DFA650E2B04E0875EEB1@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E05C742F1@onstor-exch02.onstor.net>
From: "Eric Barrett" <eric.barrett@onstor.com>
To: "Sandrine Boulanger" <sandrine.boulanger@onstor.com>,
	"Dave Limato" <dave.limato@onstor.com>,
	"dl-Design Review" <dl-designreview@onstor.com>,
	"dl-Marketing" <dl-marketing@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C8757D.ABA4A1EA
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

We should not prevent it, since the labels are meaningless.  If they had
some actual weight in that they always accurately reflected the RAID
type as given by the array, it would make sense to do so.


> _____________________________________________=20
> From: 	Sandrine Boulanger =20
> Sent:	Friday, February 22, 2008 9:39 AM
> To:	Dave Limato; dl-Design Review; dl-Marketing
> Subject:	RE: do we support volumes with multiple raid levels
> luns?
>=20
> I know there are ways to do it, but should we prevent it or not. I
> want an official answer.
>=20
> _____________________________________________
> From: Dave Limato=20
> Sent: Friday, February 22, 2008 9:25 AM
> To: Sandrine Boulanger; dl-Design Review; dl-Marketing
> Subject: RE: do we support volumes with multiple raid levels luns?
>=20
> Why yes Sandrine, I believe we do, but I think it is somewhat
> difficult to support because of the artificial raid levels.
>=20
>=20
> _____________________________________________
> From: Sandrine Boulanger=20
> Sent: Tuesday, February 19, 2008 8:20 PM
> To: dl-Design Review; dl-Marketing
> Subject: do we support volumes with multiple raid levels luns?
>=20
> Our lun labeling has a string for raid level as a parameter. Even we
> can artificially label luns as Raid-5 even if the physical read level
> on disk id Raid-0, do we support mixing physical raid levels within
> the same volume?=20

------_=_NextPart_001_01C8757D.ABA4A1EA
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: do we support volumes with multiple raid levels luns?</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">We should not prevent it, since the =
labels are meaningless.&nbsp; If they had some actual weight in that =
they always accurately reflected the RAID type as given by the array, it =
would make sense to do so.</FONT></P>
<BR>

<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Sandrine Boulanger&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Friday, February 22, 2008 9:39 AM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Dave Limato; dl-Design Review; dl-Marketing</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">RE: do we support volumes with =
multiple raid levels luns?</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">I know there are ways =
to do it, but should we prevent it or not. I want an official =
answer.</FONT>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Dave Limato<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Friday, February 22, 2008 9:25 AM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Sandrine Boulanger; dl-Design Review; dl-Marketing<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: do we support volumes with multiple raid =
levels luns?</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Why yes Sandrine, I =
believe we do, but I think it is somewhat difficult to support because =
of the artificial raid levels.</FONT></P>
<BR>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Sandrine Boulanger<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Tuesday, February 19, 2008 8:20 PM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> dl-Design Review; dl-Marketing<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> do we support volumes with multiple raid =
levels luns?</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Our lun labeling has a string for raid =
level as a parameter. Even we can artificially label luns as Raid-5 even =
if the physical read level on disk id Raid-0, do we support mixing =
physical raid levels within the same volume? </FONT></P>

</BODY>
</HTML>
------_=_NextPart_001_01C8757D.ABA4A1EA--
